Extensible Permissions for Administrative and Target Permissions

ABSTRACT

A method and apparatus for providing resource access to a user within a computer network of the automatic contact distribution system. The method includes the steps of providing a permission set that defines a limited set of features within the computer network that the user can access, the user signing into the computer network of the automatic call distribution system, the system retrieving the permission set for the user and the system providing the user with limited access to the computer system based upon the permission set.

FIELD OF THE INVENTION

The field of the invention relates to computer systems and moreparticularly to interconnected computer systems.

BACKGROUND OF THE INVENTION

The difficulty of providing access to users within interconnectedcomputer systems is generally known. One or more interconnectedcomputers are typically required whenever the task is too large for asingle computer or where specific tasks are provided by differentindependent systems and the activities of the computers must becoordinated.

Automatic call distributors (ACDs) are an example of such a situation.ACDs are typically used by telemarketers and/or service providers andare typically provided with a host computer that makes and receivescalls.

Within the ACD, workforce management, and performance optimizationsystems (operating within an ACD or otherwise) are examples of thedifferent tasks that may be distributed over a number of hosts. Inaddition to making and receiving calls, the host of an ACD may also actas a repository of customer records.

In order to reduce telephone costs, telemarketers often locate a numberof ACDs of an ACD system near major metropolitan areas. However, duringperiods of overload calls may be handled through any ACD of the ACDsystem. As a result, the host or hosts of each ACD must be accessiblefrom any agent station throughout the system.

While the interconnecting of hosts of ACDs works relatively well, theproblem of access is difficult to administer. The difficulty oftenarises because of the need for security and because of a need of a userto access many different databases. Often the only way of providingaccess to the user into different databases of the system is to manuallysave a name and password of the user into each different host.

The need for the manual entry of authorization data to gain access tothe different databases is slow and cumbersome. Because of theimportance of ACDs and of interconnected computers, a need exists for abetter method of providing access rights to users within such computersystem.

SUMMARY

A method and apparatus for providing resource access to a user within acomputer network of the automatic contact distribution system. Themethod includes the steps of providing a permission set that defines alimited set of features within the computer network that the user canaccess, the user signing into the computer network of the automatic calldistribution system, the system retrieving the permission set for theuser and the system providing the user with limited access to thecomputer system based upon the permission set.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an automatic contact distribution system inaccordance with an illustrated embodiment of the invention.

DETAILED DESCRIPTION OF AN ILLUSTRATED EMBODIMENT

FIG. 1 is a block diagram of a networked computer system 10 showngenerally in accordance with an illustrated embodiment of the invention.Under the illustrated embodiment, the system 10 allows access to thevarious features of the system 10 based upon a set of extensiblepermissions assigned to each user. The permissions are extensiblebecause the permissions are based upon a continuum of access rather thanupon the firewall-related concept of access versus no access. Under oneembodiment, the extensible permissions are embodied in a variableinterface presented to each user based upon an extensible permissionset. The interface is variable because the graphical tools provided to auser are dependent upon the rights and privileges that have beenassigned to the user.

In general, the computer system 10 may be an automatic contactdistribution system 10 having at least one host 12 that provides aunified command and control of one or more ACDs 14, 16 included withinthe system 10. The ACDs 14, 16 may be legacy or relatively new ACDs. Inthe case where the ACDs 14, 16 are a mix of conventional and legacysystems, a respective terminal adapter 18, 20 may be used to adapt theinstruction sets and protocols of the ACDs 14, 16 to the host 12.

Each ACD 14, 16 may include one or more servers. Servers that may beincluded in each ACD 14, 16 may include automatic configuration servers26, call or contact distributors 28, workforce management (WFM) servers30 or quality management (QM) servers 32.

The host 12 may include one or more command and control servers 22. Theservers 22 may be accessed by one or more desktops 24 operating on a PCconnected to the host 12.

The host 12 and servers 22 may be used to provide administrative andcontrol support for enhanced use of the ACDs 14, 16. For example, theACDs 14, 16 may be located in remote geographic areas and processcontacts with clients through a local connection to one or morecommunication systems (e.g., the PSTN, the Internet, etc.). As the callsare processed by the ACDs 14, 16, a supervisor working through thedesktop 24 may monitor a call loading of the ACDs 14, 16. By being ableto monitor a loading of each ACD 14, 16, the supervisor may detectoverloaded agent groups, adjust the number of agents available for eachcall type, and even change a criteria for routing of calls among theACDs 14, 16.

In order to adjust the number of agents available for each call type,the supervisor may need to first log into the various ACDs 14, 16. Oncelogged into an ACD 14, 16, the supervisor may be free to alter the sizeand content of the agent groups. In this regard, the supervisor maytransfer agents among agent groups of an ACD 14, 16 or even alter thecontact routing criteria that causes calls to be routed to anyparticular call group among the ACDs 14, 16.

Similarly, each ACD 14, 16 may include a local supervisor workingthrough a desktop 34 (local supervisor 34) and a number of agents, alsoworking through respective desktops 36. The agents 36 may receivecontacts from clients through a local connection (not shown) to acommunication system (e.g., PSTN, Internet, etc.).

In all cases, permissions may be based upon a permissions listassociated with one or more access points through which the user logsinto the system 10 or subsystem. For example, when the supervisor loginto the system 10 through the desktop 24 (the supervisor and desktophereinafter sometimes referred to as the supervisor 24), the UCC server22 may download a user client 38 to the supervisor for display on thedesktop 24. The user client 38 may request entry of a set of usercredentials (e.g., name and password, token key, etc.). Once thesupervisor 24 enters his/her credentials, the user client 38 maytransfer the credentials to an access processor 40. The access processor40 may compare the credentials with a set of locally stored credentialsor may access a set of security features (e.g., a Windows securityfeature) to confirm that the supervisor has authorization to access thesystem 10.

In addition to confirming the authorization of the supervisor 24 tooperate on the system, the access processor 40 may also retrieve a listof permissions 42. The list of permissions 42 may be a structureincluding a hierarchy of levels that define what the supervisor 24 isallowed to do within the system 10. For example, a first highest levelof permissions may be a first set of features (e.g., a list of domains)that the supervisor 24 is allowed to access. Below the list of domainsmay be a second set of features (e.g., a list of servers) within eachdomain that the user is allowed to access. Below the list of servers maybe a list of a third set of features (e.g., a list of data structures)that the supervisor 24 may access within each server. Below the list ofdata structures may be a fourth list of data access features that definewhat the supervisor 24 is allowed to do within that data structure. Forexample, the list of data access features may be programs that read thedata and prepare reports. In this case, if the permissions list permits,then the supervisor 24 may be allowed to edit what is included withineach report. On another level, the data access features may definewhether the supervisor 24 is only allowed to read the data or is alsoallowed to enter, modify and/or delete data.

In effect, the permissions list may be used in any of a number of waysto facilitate access within the system 10. Under some illustratedembodiments, the permissions within the hierarchy may be affirmativeand/or negative. In other illustrated embodiments, the permissions maybe based upon a class or type of access, upon specific identifiersand/or upon descriptive identifiers of the system features to which theuser is to be allowed access.

The list of permissions may be used by access processor 40 to displayfeatures of the system 10 to which a user is to be allowed access. If auser is allowed access to a feature, then that feature may be displayedin the form of an access option. If the user is not to be allowed accessto a feature, then the access option may not be displayed on a desktopof the user.

For example, if the supervisor 24 is a system supervisor concerned withthe operation of the system 10 as a whole, then the supervisor 24 may beable to access most features within the system 10. In this case, aportion of the permissions list 42 may contain an affirmative indicationof “all” to indicate that the system supervisor 24 has access to allportions of the system 10. On the other hand, in a negative limitationsportion of the permissions list 42, an indication of “passwords” may beprovided to prevent access by the system supervisor 24 to other user'spasswords. It should be noted in this regard that preventing the systemsupervisor 24 from accessing other user's passwords would not preventthe system supervisor 24 from resetting other user's passwords shouldthe need arise.

During use, the access processor 40 may use the permissions list todisplay access options on the desktop of the supervisor 24. For example,once the system supervisor 24 signs into the system 10, then the accessprocessor 40 may retrieve the permissions list 42 for the supervisor 24and begin displaying access options (e.g., icons, menus, etc.) 46, 48 ofthe system 10 on the desktop of the supervisor 24.

In order to begin displaying access options 46, 48, the access processor40 may send one or more system access queries to an LDAP server 44.Since the system supervisor 24 would have broad access to the system 10,the system queries may not be limited in any way. The LDAP server 44 mayrespond with a list of system identifiers. Included within the list ofidentifiers may be an identifier of each of the ACDs 14, 16 and also ofany other servers present within the host 12.

In response to the list of ACDs 14, 16, the access processor 40 maygenerate and cause an icon 46, 48 of each respective identified systemto be displayed on the desktop of the supervisor 24. If the supervisor24 should activate the icon 46, 48 associated with the ACD 16, then anadditional set of icons 46, 48 may be displayed representing therespective servers 26, 28, 30, 32 of the ACD 16.

On another level, another permission list 42 may also be provided forthe local supervisor 34. In this case, the permissions list 42 maycontain an affirmative permission for any system within the ACD 14 towhich the local supervisor 34 is connected. The permissions list 42 mayalso contain negative permissions for at least some subsystems withinthe ACD 14.

For example, the local supervisor 34 may be given full access to the WFMserver 30. Within the WFM server 30, the local supervisor 34 may performa number of tasks directly related to resources (e.g., agents, agentgroups, call routing parameters such as ANI, DNIS and/or URLs, etc.) ofthe ACD 14. The tasks performed by the supervisor 34 may updatingresource information (e.g., add and delete agents from agent groups,create agent work schedules and amend as necessary, enter or changeagent skills, etc.).

On the other hand, the local supervisor 34 may be given only limitedaccess to the QM server 32. Limited access in this case may beaccomplished within the permission list 42 by providing a hierarchy ofsystems to which the supervisor 34 is to be given access. In this case,the affirmative portion of the permissions list 42 may include anidentifier of the QM server 32 followed by a concatenated list ofidentifiers of subsystems and data structures that the supervisor 34 isallowed to access. In this regard, the hierarch may have one or morepaths from the highest level of the hierarchy. At the bottom of eachpath of the hierarchy free access may be given to any feature below thebottom level. On the other hand, access not provided to any parallelpaths not contained within the hierarchy.

For example, the supervisor 34 would be required to enter theidentifiers of new agents into agent lists of the QM server 32 forpurposes of tracking the performance of new agents as well as to deleteidentifiers of terminated agents. The supervisor 32 would also be ableto read the performance results of individual agents. The supervisor 32,however, would not be allowed to change performance results ofindividual agents. As a consequence, the permissions list 42 for thesupervisor 34 would include a hierarchy that includes the QM server 32with at least two paths leading from the QM server 32. One path wouldextend to an agent information server. Since the supervisor 34 wouldhave full access to the agent information server, the permissions list42 would not have any negative limitations regarding the agentinformation server.

The permissions list 42 may also have a second path from the QM server32 to an agent performance reports server within the QM server 32. Inthis case, the supervisor 34 may be able to read and print reports, butwould not be able to alter and save any report changes. Accordingly, inaddition to an affirmative permission to access an agent performancereports server, the permissions list 42 may also include a negativelimitation that prevents the supervisor from making changes to thereports server.

In this case, once the supervisor 34 logs into the QM server 32, theaccess processor 40 may provide an icon 46, 48 for accessing the agentinformation server and an icon 46, 48 for accessing the agentperformance reports server. On the other hand, since the supervisor 34would only have read access within the agent performance reports server,the access processor 40 would modify the toolbar present on the agentperformance reports control screen. In this regard, since the supervisor34 does not have write access, the control screen would not have a SAVEor any comparable softkey. In this way, the supervisor can read andprint agent reports, but cannot alter the reports.

As another example, access to the system 10 by each of the agents 36 mayalso be controlled by a respective permissions list 42. In this regard,the agents 36 may have access to a database server 50 and a transactionsserver 52. The database server 50 may provide a searchable interfacethat allows agents to search for answers to questions posed by clients.The transaction server 52 may be used by the agents to record thesubstance of transactions with clients.

The agents 36 may also have read access to the WFM server 30. Access tothe WFM server 30 may be provided to allow agents to track theirscheduled working hours.

In this regard, the permissions list 42 of each agent would includeaffirmative limitations including the transaction server 52, databaseserver 50 and the WFM server 30. However, the access may be limited inall cases. For example, the transaction server 52 may allow read andwrite access, but not deletions. The database server 50 and WFM server30 may allow read, but not write. In each case, the permissions list 42of each agent would include a delete negative limitation for thetransaction server and a write and delete negative limitation for thedatabase server 50 and WFM server 30. As above, these permissions may beimplemented within the access processor by deleting the correspondingDELETE and/or WRITE softkeys from the toolbars of the agents in thosecases where an agent 36 has reason to access the respective servers 30,50, 52.

In another embodiment, the access processor 40 may be located within abrowser 54 of a desktop used by a supervisor 24, 34 or agent 36. In thiscase, the access processor 40 may use the permissions file 42 to detectactivation of softkeys that are not allowed by the permissions file 42and delete any packets associated with the activation.

Under this embodiment, each time a supervisor 34 or agent 36 signs intothe ACD 14, a respective icon 46, 48 will be presented on the desktop ofthe user 34, 36 for each server 26, 28, 30, 32, 50, 52. Each time a user34, 36 activates an icon 46, 48 or element of a toolbar, the activity iscompared by the access processor 40 with the permissions file 42. If theactivity is not allowed by the activity file 42, then the action iscanceled.

A specific embodiment of method and apparatus for controlling accesswithin different domains of a computer system has been described for thepurpose of illustrating the manner in which the invention is made andused. It should be understood that the implementation of othervariations and modifications of the invention and its various aspectswill be apparent to one skilled in the art, and that the invention isnot limited by the specific embodiments described. Therefore, it iscontemplated to cover the present invention and any and allmodifications, variations, or equivalents that fall within the truespirit and scope of the basic underlying principles disclosed andclaimed herein.

1. A method of providing resource access to a user within a computernetwork of the automatic contact distribution system comprising:providing a permission set that defines a limited set of features withinthe computer network that the user can access; the user signing into thecomputer network of the automatic call distribution system; the systemretrieving the permission set for the user; and the system providing theuser with limited access to the computer system based upon thepermission set.
 2. The method of providing resource access as in claim 1wherein the permission set further comprises identifiers of a pluralityof servers within the computer system that the user can access.
 3. Themethod of providing resource access as in claim 2 wherein the permissionset further comprises of a plurality of features within at least some ofthe plurality of servers that the user can access.
 4. The method ofproviding resource access as in claim 3 further comprising displaying aset of access options on a desktop of the user where each access optionof the set corresponds to a respective server and/or feature of thecomputer system.
 5. The method of providing resource access as in claim3 wherein the access options further comprise icons.
 6. The method ofproviding resource access as in claim 4 further comprising the userselecting a option of the set of options and receiving access to acorresponding server of the plurality of servers.
 7. The method ofproviding resource access as in claim 5 wherein the permission setfurther comprises a plurality of resources associated with each of atleast some of the plurality of servers to which the user is allowedaccess.
 8. The method of providing resource access as in claim 7 furthercomprising the user selecting a option of the set of options andreceiving access to a corresponding resource of the plurality ofresources associated with the at least some of the plurality of servers.9. The method of providing resource access as in claim 8 furthercomprising defining the user as a supervisor of the automatic contactdistribution system and the resource information being agent dataselected from the group consisting of agent scheduling, agent skills,group assignments and passwords.
 10. The method of providing resourceaccess as in claim 8 further comprising defining the user as asupervisor of the automatic contact distribution system and the resourceinformation being contact routing data selected from the groupconsisting of ANI, DNIS, URLs and contact routing criteria.
 11. Anapparatus for providing resource access to a user within a computernetwork of the automatic contact distribution system comprising: apermission set that defines a limited set of features within thecomputer network that the user can access; means for signing the userinto the computer network of the automatic call distribution system;means within the system for retrieving the permission set for the user;and means within the system for providing the user with limited accessto the computer system based upon the permission set.
 12. The apparatusfor providing resource access as in claim 11 wherein the permission setfurther comprises identifiers of a plurality of servers within thecomputer system that the user can access.
 13. The apparatus forproviding resource access as in claim 12 wherein the permission setfurther comprises of a plurality of features within at least some of theplurality of servers that the user can access.
 13. The apparatus forproviding resource access as in claim 12 further comprising means fordisplaying a set of access options on a desktop of the user where eachaccess option of the set corresponds to a respective server and/orfeature of the computer system.
 14. The apparatus for providing resourceaccess as in claim 13 wherein the access options further comprise icons.15. The apparatus for providing resource access as in claim 13 furthercomprising the user selecting a option of the set of options andreceiving access to a corresponding server of the plurality of servers.17. The apparatus for providing resource access as in claim 15 whereinthe permission set further comprises a plurality of resources associatedwith each of at least some of the plurality of servers to which the useris allowed access.
 18. The apparatus for providing resource access as inclaim 17 further comprising the user selecting a option of the set ofoptions and receiving access to a corresponding resource of theplurality of resources associated with the at least some of theplurality of servers.
 19. The apparatus for providing resource access asin claim 18 further comprising defining the user as a supervisor of theautomatic contact distribution system and the resource information beingagent data selected from the group consisting of agent scheduling, agentskills, group assignments and passwords.
 20. The apparatus for providingresource access as in claim 18 further comprising defining the user as asupervisor of the automatic contact distribution system and the resourceinformation being contact routing data selected from the groupconsisting of ANI, DNIS, URLs and contact routing criteria.
 21. Anapparatus for providing resource access to a user within a computernetwork of the automatic contact distribution system comprising: apermission set that defines a limited set of features within thecomputer network that the user can access; a user terminal that signsthe user into the computer network of the automatic call distributionsystem; and an access program within the system that provides the userwith limited access to the computer system based upon the permissionset.
 22. The apparatus for providing resource access as in claim 21wherein the permission set further comprises identifiers of a pluralityof servers within the computer system that the user can access.
 23. Theapparatus for providing resource access as in claim 22 wherein thepermission set further comprises of a plurality of features within atleast some of the plurality of servers that the user can access.
 24. Theapparatus for providing resource access as in claim 22 furthercomprising a desktop that displays a set of access options on a desktopof the user where each access option of the set corresponds to arespective server and/or feature of the computer system.
 25. Theapparatus for providing resource access as in claim 23 wherein theaccess options further comprise icons.
 26. The apparatus for providingresource access as in claim 25 wherein the permission set furthercomprises a plurality of resources associated with each of at least someof the plurality of servers to which the user is allowed access.
 27. Theapparatus for providing resource access as in claim 26 furthercomprising defining the user as a supervisor of the automatic contactdistribution system and the resource information being agent dataselected from the group consisting of agent scheduling, agent skills,group assignments and passwords.
 28. The apparatus for providingresource access as in claim 26 further comprising defining the user as asupervisor of the automatic contact distribution system and the resourceinformation being contact routing data selected from the groupconsisting of ANI, DNIS, URLs and contact routing criteria.
 29. A methodof providing resource access to a user within a computer network of theautomatic contact distribution system comprising: the user signing intothe computer network of the automatic call distribution system; thesystem retrieving a permission set for the user; and the systemproviding the user with limited access to the computer system based uponthe permission set.